Installation

The requirements in the Generic ABI should be expanded to include the notion that an optional product should be structured into the following hierarchy: 
/opt/<pkg>/bin        - executables invoked by users
/opt/<pkg>/lib        - libraries and other executables
/opt/<pkg>/man        - manual pages
/opt/<pkg>/include    - include files
Additionally, a MIPS ABI platform will provide the following directories: 
/opt/bin
/opt/man
/opt/include
The installation script of an installable package may symbolically link files from directories under /opt/<pkg>/* to the corresponding directory under /opt . For example, the post installation script for a package called xtank , might contain the following instructions: 
for file in /opt/xtank/bin/*
do
     ln -s $file /opt/bin
done
This is especially important for manual pages in order to limit the proliferation of directories containing manual pages.

ISVs must be aware of the potential name space conflicts in the /opt directory tree. Not only must package names be unique, but individual binaries must also have names likely to be unique, since each package may link its files into /opt/bin , /opt/lib , etc.



Devices

The following devices may be available:

The devices listed here are supported for installation purposes only and are not guaranteed to generate installation media. Also, these /dev/abi nodes will exist only if the device is supported on the system.



Back to the Table of Contents
Back to the MIPS ABI Home Page


Maintained by webmaster@mipsabi.org
last modified on August 17, 1995

Copyright © 1995, MIPS ABI Group, Incorporated.